[pic] Microsoft® Office White Paper Microsoft® Schedule+ for Windows® 95 Group Scheduling Interoperability Notes [pic] A non-technical explanation of the level of communication between Schedule+® for Windows® 95 and other applications and servers. This document is a non-technical explanation of the level of communication between Microsoft® Schedule+® for Windows® 95 and other applications and servers. It is designed to help a layman, salesperson or business manager understand how Schedule+ for Windows 95 will work under different environments. This document does not serve as a technical explanation or an instruction book on how to set up a network to take full advantage of Schedule+. Interoperability Diagram The diagram on the next page describes how well different programs and servers communicate. Arrows with descriptions show the level of communication between servers. Unless otherwise noted, the communication between one application and another on the same server include all levels of information. Three kinds of information can be shared between Schedule+ and other applications are: • Meeting requests • These are the forms that Microsoft Exchange provides for sending meeting requests via email. These can be read as email and also have some of its information understood by Schedule+ (like meeting times). Sometimes, only textized meeting requests are possible, which are email messages that have all the meeting information included in the body of the message only. • Free/busy information • On the Planner tab in Schedule+, a meeting organizer can add specific people to a list of invitees, and then check their availability before scheduling a meeting. Their busy times appear in the Planner. • Details • If an invitee has given the meeting organizer permission to view the details of his or her schedule, the meeting organizer can right-click on a busy time for that person and view the details of an appointment, such as location, purpose of the meeting, etc. Details also include access to other information like contacts and tasks if the owner has given appropriate access permissions. Use this information with the diagram on the next page to understand how different applications communicate. For example, users get all three levels of information between Schedule+ 7.0 for Windows 95 on a Microsoft Exchange server to Mac™ Schedule+ 7.0 on a Microsoft Exchange server. (Mac Schedule+ 7.0 will ship approximately 6 months after RTM of Microsoft Exchange.) However, Schedule+ 7.0 on a Microsoft Exchange server to Schedule+ 7.0 on a MS Mail server gets all levels of information except details. [pic] Diagram Notes Note A Lotus has announced that they will be writing a valid MAPI driver that would permit better communication with Microsoft Exchange servers. Specifically, this would mean that Meeting Request Forms could be shared and might also mean, depending on the level of work Lotus does, that Free/Busy and Details information could also be shared. Note B Although Schedule+ 7.0 users can view Schedule+ 1.0 details, users of Schedule+ 1.0 will not be able to view details of a Schedule+ 7.0 user. Note C Only Textized Meeting Requests can be shared with these applications unless they include valid MAPI drivers. See “Schedule+ on other servers” below. Note D For all three levels of communication between a Microsoft Exchange Server and PROFS, the PROFS server requires a gateway provided by AttachMate. Client-Server Technology Clients are the applications that run on your PC. Clients on several PCs are connected to a server that resides on the backend. Client-server technology divides the work between your PC and the backend server, giving the user more functionality with less work on his own PC. For example, when a meeting request comes from a location in a different time zone, the server translates that message into your local time zone. The user gets the benefit of being able to easily schedule meetings in different time zones even though the work to make that happen did not happen on his own PC. Schedule+ for Windows 95 on an Exchange Server uses Client-server technology. Clients Using Schedule+ 7.0 in group-enabled mode always requires the Microsoft Exchange client on the front end. Similarly, using Schedule+ 1.0 in group- enabled mode always requires the Microsoft Mail client on the front end. However, these components are not interchangeable. For example, you cannot run the Exchange client with Schedule+ 1.0, or the Mail client with Schedule+ 7.0. The combination of Schedule+ 7.0 and the Microsoft Exchange client can be used against any fully compliant MAPI backend. So, although Schedule+ 7.0 is tightly integrated with the Microsoft Exchange Server and utilizes many of its capabilities for group scheduling, it will also work against a Mail 3.X server in a similar fashion to the way that Schedule+ 1.0 works today. Microsoft Exchange Server Using Schedule+ 7.0 with the Microsoft Exchange Server requires no administrative intervention. A hidden public folder is automatically created on each Microsoft Exchange Server for storing free/busy information. Any changes made to a particular user’s free/busy information are automatically replicated to other Microsoft Exchange Servers to be accessed by other users. Schedule+ 7.0 details information for each user is stored both locally, in a .SCD file, and in the mailbox on the Microsoft Exchange Server. Other Schedule+ 7.0 users can access the details for a particular user if they have access to that user’s mailbox and have been given rights to the proper folder. Schedule+ on other servers In conjunction with the Microsoft Exchange client, Schedule+ 7.0 can be used against other mail servers for which a MAPI driver has been written. Schedule+ will use that driver for sending and receiving meeting requests. It is up to the driver vendor to ensure that their driver is MAPI compliant. If there is no MAPI compliant driver, textized meeting requests can still be exchanged. Access to free/busy information and details requires that the MAPI driver vendor provide a way for the Schedule+ files to be administered on their system. A transport specification, provided in the Microsoft Exchange Development Kit, will give vendors the ability to specify for their administration modules where Schedule+ can find users' server files on their system for free/busy lookup and calendar access. The transport is a simple text file that resides on a server and maps the mail address of a user to the location of that user's Schedule+ file. Additional Questions For more in-depth information, please see \\wgamktg\push\products\schedule\sourcebk\confin.doc. ######### ( 1995 Microsoft Corporation. All rights reserved. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. Microsoft, Windows, IntelliSense, TipWizard, PivotTable, PowerPoint, Visual Basic, and the Office Compatible logo are either registered trademarks or trademarks of Microsoft in the United States and/or other countries.